Ops Center: audit vs authentication logs; three paths to Org Admin - #99

…rg Admin

Processes four reviews from Vijay Venkataraman.

team/2026-09-04--f4fc1c8a — "how do i access audit logs in ops center" was answered
with the authentication-logs material, which is the wrong log type. Ops Center has no
audit/activity logs today; activity data comes from a ticket, and Activity logs against
a Product Registry product and an organization are planned but not shipped. New
FAQ-OpsCenter entry covering the distinction, the ticket route, and why Ops telemetry
answers "is it licensed" but never "who licensed it".

The same entry also fields "who licensed a product for a workspace?", and flags that
such a question is usually really about workspace availability rather than org-level
licensing.

Because retrievers chunk independently of headings, a question about audit logs
retrieves the Authentication logs table rather than the FAQ entry that governs it. The
warning is therefore repeated at that table in Docusaurus-OpsCenter.md, marked as an
authored addition so a re-derivation from Blueprint restores it.

team/2026-09-08--4125fbd2 — "how to add myself as an admin" got the ticket route and
the Manager's Guide, but presented the guide as the way to get access. For someone who
already holds the self-promotion permission the answer is one in-product action and no
request at all. The existing FAQ entry went from two paths to three, splitting "use the
permission you have" from "obtain the permission", and now says to check which case the
user is in first. Adds the expectation that Tyler staff self-remove Org Admin rights
when done.

bp-general/2026-09-08--746ef8a4 and team/2026-09-08--fb1ea5c4 — closed out. Both carry
correct/good/n-a verdicts with empty review blocks; only action_status was left open.

Verdicts were not touched. fix_target and kb_action were the untouched form defaults on
both actioned transcripts and were derived from the Proposed fix prose, which says to
update the KB in each case; each transcript's notes field records that.

Claude-Session: https://claude.ai/code/session_01KxA7f912exehyUjjgVBgf4

Vijay's correction on the review of team/2026-09-04--f4fc1c8a: "TCP Audit log
currently only exists in Audit Center that is only for OneTyler staff. There is no
Tyler wide tool that gives Audit/Activity logs excepting Authentication logs which is
available in Ops Center."

This is the reason the ticket route exists, so the entry now says so rather than
listing a request as an unexplained first step. It also stops the agent suggesting
"check the audit logs" to a general Tyler audience who cannot open the tool.

Audit Center is owned by Knowledge-BP-General/Docusaurus-OpsApps.md, whose upstream
Blueprint page is a stub, so this restriction is currently written down nowhere else.

Claude-Session: https://claude.ai/code/session_01KxA7f912exehyUjjgVBgf4

…esearched

Vijay confirmed 2026-09-09 that Activity logs are expected in Ops Center soon with no
date available, and that he will flag when it lands. Noting it in Promote when so a
later session does not re-litigate the missing date or soften the not-shipped wording.

Claude-Session: https://claude.ai/code/session_01KxA7f912exehyUjjgVBgf4

corpdev-new-blueprint#1585 corrects the Workspace terminology entry (it claimed a
workspace is 1:1 with a tenant), tightens Tenant to match, and stops the Ops Center
workspaces guide describing a workspace as an environment. The KB half of this review
was already on main, which is what made the Blueprint half easy to lose: the knowledge
files are derived from those pages, so the next reconciliation would have reverted it.

review_status stays pending - that is the reviewer's to set.

Claude-Session: https://claude.ai/code/session_01KxA7f912exehyUjjgVBgf4